
APAR= II09358
CAWIN COMMUNICATIONS RESAVE TIPS


** Last update 3/28/97 **

The following PTFs have been released to improve the
support for Wide Area Network (WAN) connections (SDLC, Async
and X.25).  The PTFs are listed with the SBCS PTF on the left
and the DBCS PTF on the right, followed by a description of
the changes.  Note:  the first group of PTFs are all
co-requisites and the following are all individual PTFs.

SF28513 / SF29443  Communications code changes
SF29224 / SF29490  Enhancements for WAN configuration to
          SF29569  support the communications code changes
-------------------------------------------------------------
SF28956 / SF29505  Package file changes for install and update
                   support of new communications code
SF29519            Connection program change to not display the
                   message "Place call to host now"
SF29954            Include the replacement text for message 5147
SF29442            Additional validation of configuration
                   parameters

These PTFs provide an improved implementation of how SDLC and
ASYNC connections will activate in the Windows 3.1 client. The
code is based on how the Client Access DOS SDLC and Async
routers set up connections.  Please follow these instructions
carefully. Your AS/400 should be at the latest cumulative
PTF package before these PTFs are applied.

*** NOTES for SDLC CONNECTIONS ***

With certain versions of SDLC Adapters, the adapter may need
the Data Set Ready (DSR) signal active in order to send the
V25Bis Command to the Modem. It is best to configure your
modem to have Data Set Ready behave in one of the following
ways:

1) Have DSR follow Data Terminal Ready (DTR)
   (option on IBM 5853 Modem) or
2) Have DSR ON "USUALLY" (an option on IBM 7855 Modems) or
3) Have DSR ON ALWAYS (some OEM Modems have this option).

Also, your modem must be able to handle the Auto-Dial Command
in the same Data Encoding Mode (NRZI entry) as your normal
datastreams. Most IBM modems will recognize a V25Bis Command
in either NRZI Mode YES or NRZI Mode NO.  Most OEM modems only
recognize a V25Bis command in NRZI Mode NO.

The SDLC adapters supported today use IRQ3 and IRQ4
for hardware Interrupts.  This means that you cannot use
a serial mouse that runs off of one of these interrupts.
You can use a Bus Mouse on PC's that have an SDLC Adapter
installed.

For SDLC, this code will allow multiple responses to come back
from the modem to indicate that a connection has completed.  The
only responses that the code will not accept are those
beginning with "CFI" (standard indication that the call
failed), or "INV" (an indication that the PC sent an INVALID
Command).

The SDLC Connection has been verified with the following
IBM Switched SDLC modems (this list will be added to as
additional modems are tested):

a) IBM 5853 2400 bps  SYNC modem
b) IBM 7855 12000 bps SYNC modem
c) IBM 7852 Mod 13    SYNC modem

For SDLC Multi-Point, these SDLC Options should be set
as follows:

Set NRZI Mode = NO on all PC's and on the AS/400 SDLC line
description.  Set SDLC (Line Facility) = HALF Duplex on ALL
PC's and AS/400 Line.  Set Line Type = NON-Switched
Point to Point connection

Even though there is no option to set Multi-Point in the
PC configuration of the connection, the connection should
work provided the above parameters are set.

The SDLC Adapter uses Direct Memory Access Channel 1, so any
other devices that use DMA's must use a different DMA channel.

d) IBM 7857      SYNC modem

For SDLC/switched, these SDLC Options should be set:

  Modem settings:
    1) set D12 configuration: select factory #3
    2) set D11: V25 HDLC NRZI-ASC
    3) set U12 C107/C109: C107 ON / C109 CTRL
    4) set U13 C107 (SDR): follow C109 (CD)

  AS/400 SDLC line configuration: NRZI = YES
  CAWIN configuration: Advanced Options, NRZI = YES

***  NOTES for ASYNC CONNECTIONS ***

The code will attempt to set up the modem using the modem init
string provided by the .PIF file.  It will then attempt to
dial the AS/400 and determine when the connection to the
AS/400 modem has completed.  Its primary method for determining
that will be to monitor the RS-232 signals from the modem.
Once the modem indicates that a connection is complete, then
the code will attempt to communicate with the ASCII work
station controller. Note that this is slightly different than
what the DOS router did (The DOS router would look for a SWAR
string from the modem if a SWAR entry was in the CONFIG.PCS
file).

The .PIF files for the following modems have been verified to
work to an AS/400 ASCII work station controller that has one
of several different modems connected to it (this list will
be added to as additional modems are tested):

PC modem                     speed    AS/400 modem
--------                     -----    ------------
IBM 7855                     12000    IBM 7855
IBM 7857                      9600    IBM 7857
IBM 7852 Mod 13              28800    IBM 7852 Mod 13
IBM PCMCIA 14.4              14400    Hayes Optima 28800
Hayes Optima 28800           28800    Hayes Optima 28800
MegaHertz XJ1144FM           14400    Hayes Optima 28800
Practical Peripheral 14.4    14400    Hayes Optima 28800
US Robotics Sportster 14.4   14400    Hayes Optima 28800

Also, tests were performed through a leased line modem setup
(using 2 IBM 7855 modems running in leased line mode).

*** NOTES for X.25 PAD Connections ***

The APPC controllers configured on the AS/400 must have the Data
Link Role parameter (*ROLE keyword) set to *NEG (Negotiable).
This will allow either the older WIN/16 X.25 code or the new
code in this PTF to connect to the AS/400.

Also, the following are suggested Timer/Retry Parameters on the
APPC Controllers that are used for the WIN 3.1 X.25 PAD Clients:

 X.25 frame retry . . . . . . . . :   7
 X.25 connection retry  . . . . . :   50 (50 Tenths of a second)
 X.25 response timer  . . . . . . :   80 (80 tenths of a second)
****************************************************************

In order to tailor the operation of the VDWAN.386 module, the
code can read entries out of the SYSTEM.INI file that is located
in the directory where Windows is loaded from.  It will read
parameters out of the section called VDWAN.  The following
describes the parameters, and why they might be needed.

  UseFifo=FALSE                 default is TRUE

    If the specified UART supports FIFO, by default FIFO
    is used at the rate of 8 bytes per interrupt in the receive
    direction, and 16 bytes per interrupt in the send
    direction (a FIFO UART is a NS16550A or equivalent UART),
    Specifying UseFifo=FALSE results in the UART being treated
    like the 8250 non-FIFO UART; that is, only one byte is
    received or sent per hardware interrupt.  This parameter has
    no effect for SDLC.  This parameter may be needed if you
    wish to prevent the code from using the advanced functions
    of the FIFO UART. When the 8250 UART function is used (or
    the UART hardware is an older 8250 UART), the baud rate
    will be set at 9600 bps.

  FifoMaxRcv=4                  default is 8

    Valid values are 1, 4, 8, and 14.
    This value is the number of bytes that will trigger a
    receive interrupt to occur when running the 16550A in FIFO
    mode.  This value may need to be adjusted if you are
    experiencing overruns due to another Windows application
    holding off interrupts for a long time while data is
    coming in for the ASYNC or X.25 router.

  IRQNum=03h                    default is 3 and 4

    By default the code will install in both IRQ3 and IRQ4.
    Specifying this parameter results in only that one IRQ
    being used.  This parameter can be used to eliminate IRQ
    conflicts for modems that have a programmable IRQ.  This
    parameter cannot be used with SDLC.  This parameter is
    required if you are using a serial mouse along with the X.25
    or ASYNC connections. Specify which IRQ you want the Windows
    router code to use, and the other interrupt can then be
    used for the serial mouse.

  ComPortBase=03e8h             default based on COM port number

    By default the code uses COM port bases as follows (based
    on the COM Port that you chose through the configuration
    program):

      COM1      03f8h
      COM2      02f8h
      COM3      03e8h
      COM4      02e8h

    If your COM port use some other starting port address, then
    use this parameter to tell our code what that starting port
    address is.  This parameter is valid for ASYNC and X.25
    connections.

Valid values for any BOOLEAN parameter are as follows:

  TRUE, 1, Yes, ON, FALSE, 0, No, OFF

Other language-specific values may also be valid.  All of the
strings are case-insensitive; that is, the following is valid:
(Note: Because of a problem with printing square brackets,
all places that require a square brackets have been changed to
less than "<" and greater than ">" signs.  Make sure when
you are actually editing the SYSTEM.INI file that you use
square brackets.)

  <vdWAN>
  coMPOrtBASE=abcDh
  UseFifo=TRUE
  IRQNum=05h
  FifoMaxRcv=1

For all WAN Connections, there is an additional module called
LOGWAN.EXE, which will retrieve line status and log information
from the WAN Code. This is similar to the information presented
in the DOS Router when the STARTRTR/D command was run at the
DOS prompt.

*** SWITCHING from LAN to WAN Connections ***

There is now a method available that will allow you to toggle
easily from a LAN connection to a WAN connection without
having to reconfigure your PC through the CA/400 configuration
program. This is now possible because there are no longer any
statements for WAN connections in CONFIG.SYS or AUTOEXEC.BAT.

Follow these steps to get the initial set-up working:

1) Configure for a WAN connection.
2) Verify that the connection works.
3) Copy this file from  WINDOWS NSD.INI to  WINDOWS NSD.WAN
4) Configure for a LAN connection.
5) Verify that the LAN connection works.
6) Copy the new  WINDOWS NSD.INI to  WINDOWS NSD.LAN
7) Edit  WINDOWS SYSTEM.INI to add VDWAN.386 after the
   VD802.386 statement.  Note:  If you needed to add a VDWAN
   section, you need to enter this information again.
8) You will need to restart Windows before you can toggle
   between connections.

You can then toggle from one connection to another by
copying NSD.WAN to NSD.INI (for WAN connections) or
copying NSD.LAN to NSD.INI (for LAN connections).
A suggested way to do this is to add 2 icons into the
CA/400 program group - one that will do WAN setup,
another that will do LAN setup.

NOTE: Refer to II09711 for more information on toggling
      configuration types.
****************************************************************

LOGWAN Trace Utility User Interface
-----------------------------------
The LOGWAN Trace Utility is designed to work with the newly
rewritten WAN code. It provides a snapshot of the condition of
ASYNC, SDLC and X.25 connections established using Client
Access/400 for Windows 3.1 that has been enhanced with the
rewritten WAN code.

Using the LOGWAN Trace Utility, you can check the condition of
the connection while the code continues to run. LOGWAN collects
the data and displays it to you on the screen.
An example of the output data:

Windows started:        Thu Apr 11 15:27:59 1996
Current time:           Thu Apr 11 19:44:13 1996
Log Start time:         Thu Apr 11 17:18:51 1996

CRC     Overrun Frame   Byte    SendRetry
 0       0       0       0       0

Event Log:
Thu Apr 11 17:51:44 1996        LinkLostError   0x31

From the LOGWAN program menu file you can save this data to
a file in the CAWIN subdirectory. The name of the file is
logdata.wan.

The LOGWAN.EXE is located on the last install diskette (if the
media was ordered after April 1996).  Otherwise, you can
contact service and they can sent you a copy of the tool.

